The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

BTW, would brew (for instance) be ok with having two aliases (the current huggingface-cli and hf)? Might be worth checking with them

Played around with it locally, it works great! When using the deprecated API (like huggingface-cli login, you still get recommendations about the old API, maybe worth recommending only new APIs everywhere? But not key for this PR.

@LysandreJik I've updated all the documentation and tips to promote hf instead of huggingface-cli 6d820c4 (retrospectively I should have done it in a follow-up PR to keep this one small-ish but too late...)

One question: wouldn't it make our life simpler during maintenance and to remove the deprecation down the road, to move all commands from commands to cli while keeping a utility to still allow imports from commands, rather than copy-pasting everything?

Keeping two copies means that it's easy for the two to diverge, and I don't think we want that even through the deprecation. If the syntax is too different from the original, feel free to ignore 🤗

@LysandreJik as mentioned in DMs, I prefer to stick with the "duplicated code" approach. Even if it's not the cleanest solution, I see a few benefits to it:

• we don't touch anything to existing logic => guarantees we don't brake anything
• CLIs have slightly diverged in syntax. If I want to keep a unified logic it makes it slightly annoying to handle both in a clean way
• having separated code makes it easy to add new commands to the new CLI without adding them to the old CLI (which we don't want to extend in order to force users to use the new one)
• • hopefully we won't change much of the legacy CLI. If there are severe bugs, we will fix them but otherwise we will simply leave it as it is now without maintaining/adding new stuff to it

BTW, would brew (for instance) be ok with having two aliases (the current huggingface-cli and hf)? Might be worth checking with them

Gentle ping to @singingwolfboy on this :)

For context, we are switching the HF CLI from huggingface-cli to hf with a slightly improved syntax. For example huggingface-cli login becomes hf auth login to be closer to the well-designed GitHub's CLI. In practice, both CLIs will exist at the same time. The legacy one huggingface-cli is deprecated and redirects to hf but will still be functional. We will remove it in the future but only after a very long deprecation cycle. We promote only hf in our docs.

@singingwolfboy my questions are now: would brew be able to support 2 command lines like this? Or would it simply be a separate brew install hf command? Also the tests in this script will probably break when we release this (huggingface-cli whoami => hf auth whoami + if using legacy CLI you'll get an additional warning message). Let me know if we can help in any way 🤗

(gentle ping to @abitrolly who has maintained the brew script lately)

Thanks everyone! I'll merge this one now.

About brew (#3229 (comment)), I kept the previous huggingface-cli docs for now and we can adapt in a future PR. I don't want to make this one bigger than what it is now ^^